An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I'm posting again — and unfortunately, I already know how this thread is going to go. My app (ID: 6756186616) has now been stuck in "In Review" for 80 days. To save everyone time, here is the reply I expect to receive within a day or two, copy-pasted from the response on my last thread: "Thank you for your post. We're investigating and The App Review team will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us." Nothing actually happened after that reply last time. No follow-up in App Store Connect. No further communication. Just silence. When I escalated to Developer Support (case #20000111565861), I was told explicitly that Developer Support has no way to reach the App Review team and no authority to intervene on submissions stuck in review. So Developer Support points back to App Review, and the standard forum reply points back to "contact us" — which loops back to Developer Support. This is a closed loop that doesn't actually resolve anything for an independent developer. Concrete questions: Is there any real escalation path that doesn't end in an automated reply? Why has a submission been "In Review" for 80 days with zero communication? What should a solo developer do when both Developer Support and the forum response are dead ends? I'm not asking for special treatment. I'm asking for the review to actually move — in either direction. A rejection with feedback would be infinitely more useful than 80 days of silence. Thank you.

I am trying to submit a new app and now this message comes up: The items below are required to start the review process: English (Canada) - Privacy Policy URL - This field is required Arabic - Privacy Policy URL - This field is required Croatian - Privacy Policy URL - This field is required English (Australia) - Privacy Policy URL - This field is required Show Details What is it, and what to do? Dan Uff

I want to share how I truly feel about this situation. I have spent years building every single app on my account before publishing anything on the App Store. Each one represents months of work, testing, and genuine effort to create something valuable for users. I am proud of what I built and I stand behind every app I have ever submitted. I honestly do not believe I deserve this decision. I have never intentionally violated any guideline. I have never tried to deceive Apple or users. I have always engaged with the review process in good faith, even when it was difficult and took months. The notice itself states that automation may have been used as part of the review process. I strongly believe this was an automated mistake. A human reviewer who looks carefully at my submission history and my apps will not find evidence of concept switching or hidden features; because there is none. I am a student in France. This account is how I support myself. Losing it overnight, after years of work, without a proper human review, is devastating. I am not asking for special treatment. I am asking for a fair human review of my case before a final decision is made. Thank you for reading this.

I set up all the App Store details, including support info and other required information, but I’m having an issue when adding a build and trying to save. The Save button turns red, and I’m not sure why. It’s not showing what I’m missing in the setup.

Hi App Review Team, My app Fluto AI: Anime & Art Painter (Apple ID: 6762746586) has been in "Waiting for Review" for 17 days with no update. Quick timeline: the app was previously approved but unpublished. After minor changes I resubmitted, it was rejected and a demo video was requested. I added the public video URL to App Review Notes and resubmitted. Since then, no movement, no messages in Resolution Center, no response to my support case or expedited review request. Could someone please confirm if there's a blocker or any additional information needed? Happy to provide anything immediately. Thank you.

Dear App Review Team, I hope you are doing well. I am writing regarding our game My Garage Story (App ID: 6762339825), which has been stuck in the “Waiting for Review” status for a very long time. My Case ID is 102886678091. I have already contacted support multiple times regarding this issue, but unfortunately, we have not received a proper resolution or update yet. It has now been almost 3 weeks, and we kindly request that this matter be treated with priority and resolved as soon as possible. We currently have the game available for pre-order in the US region, and we are eagerly waiting for the review approval so we can officially launch it for iOS users. Our next build is also ready with further polish, optimizations, and bug fixes. Additionally, the same game is already live on Google Play under a changed title and the same developer account. For your reference, I am sharing the Android version link below: https://play.google.com/store/apps/details?id=com.playspare.mycardealershipsimulator We also have an active Discord community of around 400K members who have been waiting for the iOS release for quite some time. Due to the current delay, our iOS launch plans are being heavily impacted. We kindly request you once again to please review this case seriously and help us get the app into review and approved as soon as possible. Thank you for your time and support. We look forward to your response.

Dear App Review Team, We would like to kindly follow up regarding our app submission, which has been in “Waiting for Review” status since Apr 10, 2026, with no progress update to date. We have also submitted 3 expedited review requests, plus 2 support requests email but unfortunately have not received any response yet. This prolonged delay is now significantly impacting our project timeline and scheduled deployment commitments. We understand review times can vary, but it has now been over a month without movement or communication. App ID: 6752937247

I have two auto-renewable subscriptions (RedBird.Monthly and RedBird.yearly) that have been stuck in "Waiting for Review" status through 4 separate app version submissions and approvals. Each time I submit a new app version, the app itself gets approved and released, but the subscriptions remain in "Waiting for Review" and are never reviewed alongside it. I have: Added screenshots to both subscriptions under Review Information Filled in all required localization fields Submitted the app with a build attached each time Tried clicking "Submit for Review" on each subscription individually The subscriptions are part of a subscription group called "RedBird Premium." The app is a Capacitor-based iOS app (com.redbird.wellness). Has anyone experienced this? Is there a specific step required to explicitly link subscriptions to an app version submission in the current App Store Connect UI? The "In-App Purchases and Subscriptions" section described in Apple's documentation does not appear on my version page. Any help appreciated.

Hello Apple Review Team, Our app (Apple ID: 6758392381) has been stuck in “Waiting for Review” for the past 6 days. We have already contacted Apple Support and also submitted an Expedited Review Request, but unfortunately we haven’t received any response or update yet. This delay is affecting our release timeline, and we would really appreciate any guidance regarding the current status of the review. Could you please let us know: If any additional information or documentation is required from our side? If there is any issue or blocker causing the delay? We are ready to provide any details or make any necessary changes immediately. Thank you.

Hello Apple Developer community, I am seeking help with a recurring App Store rejection under Guideline 2.1(a) - Performance - App Completeness. My app crashes on launch specifically on iOS 26.4.2 and I have confirmed this is a platform-level bug in React Native — not an issue with my application code. BACKGROUND My app is Highway Exit Food Finder — a navigation utility built with Expo SDK 55 / React Native 0.83. It has been in review for several weeks and has been rejected multiple times due to a crash on launch on iPad Air M3 and iPhone 17 Pro Max running iOS 26.4.2. THE CRASH Every crash log shows the same signature: Exception: EXC_CRASH (SIGABRT) Location: ObjCTurboModule::performVoidMethodInvocation Thread: com.meta.react.turbomodulemanager.queue The crash occurs during TurboModule initialization — BEFORE any JavaScript code runs. This means no application-level code change can fix it. CONFIRMED PLATFORM BUG This crash is documented in: github.com/facebook/react-native/issues/54859 github.com/expo/expo/issues/44680 These issues confirm that React Native's New Architecture TurboModule system throws an NSException during async void method invocation on iOS 26 that cannot be caught, causing SIGABRT. WHAT I HAVE TRIED Removed expo-notifications (possible crash source) Removed react-native-maps Simplified all screens to static components Set newArchEnabled: false in app.json Upgraded to Expo SDK 55 Submitted 17+ builds attempting to fix this Despite all these changes the crash signature remains identical across all builds because the crash happens at the platform level. MY QUESTIONS Has anyone successfully gotten a React Native Expo app approved on App Store Review while running iOS 26.4.2 on review devices? Is there a known working configuration for Expo SDK 55 that avoids the TurboModule crash on iOS 26? Has anyone successfully appealed a 2.1(a) rejection caused by a platform bug rather than app code? Can Apple review devices be updated to use a stable iOS version for reviewing React Native apps while the iOS 26 compatibility issues are resolved? DEVICE AND BUILD INFO Review device: iPad Air 11-inch M3 OS: iPadOS 26.4.2 Framework: Expo SDK 55 / React Native 0.83 Build tool: EAS Build All crash logs reference the identical TurboModule crash signature Any help or guidance from the community or Apple engineers who monitor these forums would be greatly appreciated. Thank you.

Hello, I honestly don’t understand what’s going on with my app review. My app was already approved before, and I submitted a new build on April 7th with some new features and important bug fixes. Since then, it has been stuck on “Waiting for Review” with absolutely no update. It’s been 40 days now, which is honestly unacceptable. I even submitted an expedited review request, but that didn’t help either. The worst part is that this build contains bug fixes for users, and the delay is directly affecting the app experience. Waiting this long without any response or progress is really frustrating. Can someone from Apple please look into this and help resolve it ASAP? Thank you.

Hi, I've been developing and releasing apps on app store for a while now. Around 11 days ago, I sent my latest (3rd) application to review, soon enough got a rejection message with guidelines. It was normal for me because it happens on all applications, same day I addressed all issues. Uploaded a new build, wrote in review notes that what I did to fix these guideline issues. However since that time my app is stuck on "Waiting for Review" I would take that as normal but there is one strange point, when I go to "Subscription" page, my 3 subscriptions are stuck "In Review" for over 9 days. Is it because I tried to release the app directly with a subscription method included? I don't know. I can not remove the subscription now to update the app without any pro features either. Contacted Apple Developer Support, however no answers from there also. Did anyone else had a problem like this, and how did you reach to a fix? Thank you

My app has been stuck in “Waiting for Review” for a very long time and I’m honestly getting really frustrated. I already fixed all previous issues and submitted everything properly, but there has been no update at all. This delay is seriously affecting my launch plans and business operations. I understand reviews can take time, but the waiting period feels unusually long compared to my previous submissions. Has anyone else experienced this recently? Is there anything I can do to speed up the review process or get an update from Apple? I’d really appreciate any advice or shared experiences. Thank you.

Hello Apple Developer Relations / App Review Team, Our first app release has been pending review significantly longer than expected, and we urgently need assistance. We had a coordinated marketing launch scheduled yesterday based on the standard review timelines communicated in App Store Connect. The delay is now impacting launch commitments, marketing campaigns, and user onboarding plans. Current status: First app submission Build status: waiting for review No messages or requests received in Resolution Center App is fully tested and production ready We respectfully request assistance or escalation for an expedited review if possible. We understand review times can vary, but we would sincerely appreciate any help or visibility into the current delay. App name: LiveVibe App ID: 6767975462 Thank you very much for your time and support.

Hi, My external TestFlight build has been waiting for review for over 2 days with no update or response. App details: App name: Propzo Bundle ID: com.propzo.ai Version: 1.0.0 Build 2 Developer Apple ID: eswarpropzo Submitted: May 14, 2026 I have also tried contacting Apple Developer Support via the contact form but the dropdowns are not working. Has anyone experienced this delay? Is there anything I can do to expedite the review? Thank you

Hi everyone, I’m looking for guidance from developers who have dealt with App Review for health-related apps. I have an app that presents users with a questionnaire using images and multiple-choice answers. Based on the responses, the app categorizes the user into a general diabetes risk category. A few important points about the app: The app does NOT provide a diagnosis. The app clearly states that it is informational/advisory only. We added disclaimers throughout the app. We included references to published research papers the methodology is based on. The app does not connect to medical devices or Apple Health. No treatment or medication recommendations are provided. However, the app keeps getting rejected during App Review. Apple is asking us to provide documentation/approval from health regulatory authorities for every country where the app will be distributed. This is where I’m confused: Is this actually required for apps like this? Are reviewers classifying this as a regulated medical device? How are similar diabetes risk / health risk apps on the App Store handling this? Is there a recommended way to position the app as wellness/educational instead of diagnostic? We’ve already tried: strengthening disclaimers, clarifying that it is not a diagnosis, removing strong medical claims, submitting from both personal and organization accounts. Still receiving the same type of rejection. Would really appreciate advice from anyone who has successfully navigated this type of review process. Thanks!

Hey everyone, We recently submitted our new dating app, Rove Dating, and it’s been rejected under Guideline 4.3(b) — “Design: Spam.” I’d really appreciate your insights, especially from anyone who’s faced something similar or has experience getting nuanced apps approved in a saturated category. Before building Rove, we spoke to dozens of users of existing dating platforms. We consistently heard the same thing: people are deeply dissatisfied with current apps. They’re overwhelmed, burned out by swiping, and frustrated by endless choices and low-quality interactions. It became clear that the problem isn’t that there are “too many” dating apps — it’s that most aren’t adapting to how people actually want to date in 2025. We designed Rove to address those pain points head-on, with a totally different approach to matching, message limits, and emotional safety. We believe our app meaningfully improves the dating experience — but we’re having trouble getting that across in the review process. Below is the explanation we’ve been submitting, which we feel strongly communicates how Rove is different. If anyone has tips, feedback, or even just a second set of eyes on how we’re presenting this, I’d be grateful! –– Response to Guideline 4.3(b) – Design – Spam We respectfully disagree with the assessment that Rove Dating duplicates existing apps. Rove is not a clone of existing dating apps — it introduces original interaction mechanics and novel safety features designed to address the growing frustration users feel toward current dating platforms. ⸻ What Makes Rove Dating Unique Rove Dating is a highly curated experience that intentionally limits user engagement to foster more meaningful, emotionally safe interactions: Key Differentiators: • No Swiping or Infinite Browsing: Users see a small, rotating selection instead of endless feeds. • Limited Conversations: Each user can have only 3 active conversations at a time. • “Shoot Your Shot” Mechanism: • Men can initiate contact with a limited set of women. • If a woman declines, the man can try with someone else — if not, he must wait. • Women can only receive inbound messages, helping prevent message fatigue. This constraint-based system: • Reduces inbox overload (especially for women). • Encourages higher-quality, intentional messages. • Mimics real-life social dynamics — where opportunities are limited and meaningful. ⸻ Innovative Safety System: MPAA-Style Behavior Ratings Rove also introduces a first-of-its-kind safety feature inspired by the MPAA film rating system: • Male users are assigned a community-informed behavioral safety rating (e.g., G, PG, R) based on in-app messaging analysis. • Women can quickly assess a match’s tone, trustworthiness, and vibe before engaging. • This system encourages respectful behavior and promotes a safer, more transparent dating environment. This type of behavioral transparency does not exist in any other dating app currently on the App Store. ⸻ Conclusion Rove is not another swipe-based clone. It is a thoughtfully reimagined dating platform built around scarcity, respect, and intentionality. Its mechanics — from conversation caps to safety scores — are fundamentally different from other offerings in the App Store’s dating category. We hope you’ll reconsider Rove on the merits of its original features, purpose-driven design, and unique safety innovations.

Hello, I'm posting again — and unfortunately, I already know how this thread is going to go. My app (ID: 6756186616) has now been stuck in "In Review" for 80 days. To save everyone time, here is the reply I expect to receive within a day or two, copy-pasted from the response on my last thread: "Thank you for your post. We're investigating and The App Review team will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us." Nothing actually happened after that reply last time. No follow-up in App Store Connect. No further communication. Just silence. When I escalated to Developer Support (case #20000111565861), I was told explicitly that Developer Support has no way to reach the App Review team and no authority to intervene on submissions stuck in review. So Developer Support points back to App Review, and the standard forum reply points back to "contact us" — which loops back to Developer Support. This is a closed loop that doesn't actually resolve anything for an independent developer. Concrete questions: Is there any real escalation path that doesn't end in an automated reply? Why has a submission been "In Review" for 80 days with zero communication? What should a solo developer do when both Developer Support and the forum response are dead ends? I'm not asking for special treatment. I'm asking for the review to actually move — in either direction. A rejection with feedback would be infinitely more useful than 80 days of silence. Thank you.

Hello, I submitted an update for my app for review on April 27th. Since then, the app has remained in the “Waiting for Review” status. I contacted support by email after one week and again after two weeks, but both of my messages were left unanswered. Please provide me with an overview of what is going on with my app submission for review. Thank you.

Hello Apple Review Team, Our app update has been stuck in "In Review" status for almost 2 months, and we are unable to get any updates or response through the standard channels. App Details: App Name: Pomodoro Timer: CoffeePomodoro App ID: 6756186616 Version: 1.3.0 (Build 2) Submission ID: 50057266-51aa-4b7a-ad93-c3310c200f21 Date Submitted: March 15, 2026 Current Status: In Review (for ~60 days) We have already submitted multiple "Contact Us" requests through App Store Connect, but have not received any response or explanation for the extended review time. This prolonged delay is significantly impacting our release schedule and our ability to deliver bug fixes and improvements to our users. The update contains important fixes that our users are waiting for. Could someone from the App Review team please: Look into why this submission has been pending for this long? Provide an estimated timeline or any feedback if there's an issue with the build? Let us know if any additional information is required from our side? Any help or guidance would be greatly appreciated. Thank you in advance. Best regards